PC-SIG: World of Education/PC-SiG's World of Education.iso/wor/disk1664.zip/EASYTYPE.HLP

Text File | 1990-01-10 | 100KB | 1,636 lines

; Text file for EZHELP.EXE or EZHELP.COM, a menu-driven environment
; for screen/printer output. Place EZHELP and this file in the same
; directory and type EZHELP.
;
; Except as specified in the "User-Added Information" section below,
; no alterations may be made. Doing so violates the copyright, and may
; make this file unusable with the help program. Use well, and enjoy.
;
9 January 1990
9
PRINTOK
TITLE:    EASYTYPE USER MANUAL
                              USERS  MANUAL

                                -- for --


********   ******   ********  **   **  ********  **    **  ******   ******** tm
**        **    **  **         ** **      **      **  **   **   **  **
******    ********  ********     **       **        **     ******   ******
**        **    **        **     **       **        **     **       **
********  **    **  ********     **       **        **     **       ********


        THE INTELLIGENT WORD PROCESSING TO TYPESETTING TRANSLATOR
                                -- with --
        A GUIDE TO CREATING WORD PROCESSING FILES FOR TYPESETTING


               EASYTYPE / EZHELP Edition 3 License: $49.95
               Copyright (c) 1988, 1989, 1990, J. W. Olsen
                           All Rights Reserved
                        Advocate Enterprises, Ltd.
                                 Chicago
~ (Menu)
     ======================  EZHELP Run-Time Menu  ==================
     =  Q - QUIT Program                                            =
     =  A - ALL SECTIONS of File                                    =
     =  1 - Becoming Acquainted, Installation & Invoking EASYTYPE   =
     =  2 - Word Processing Files for Typesetting: The Basics       =
     =  3 - Beyond the Basics                                       =
     =  4 - EASYTYPE Run-Time Functions                             =
     =  5 - Especially for Typesetters                              =
     =  6 - Itemized EASYTYPE Translation Routines & File Analysis  =
     =  7 - (User-Added Information)                                =
     =  8 - License Agreement, Credits & Disclaimer                 =
     ================================================================
~(Section 1)
       << BECOMING ACQUAINTED, INSTALLATION & INVOKING EASYTYPE >>

   INTRODUCTION

   EASYTYPE  translates  the  files of most  computer  word  processing
   programs into the format of most typesetting systems. In addition to
   a Generic/ASCII mode which handles standard "ASCII" files most  word
   processors  can  create, this EASYTYPE version also  offers  special
   modes which directly translate codes unique to text files created by
   industry-leading  WordPerfect  and WordStar. (Note:  See  discussion
   later  in this section for discussion of special-format  files  from
   the latter programs.)

          By use of EASYTYPE, you agree to the terms and conditions  of
   the License Agreement in Section 8.

          EASYTYPE  is currently available for MS-DOS/PC-DOS  and  more
   than  100 CP/M computers. A minimum configuration of one disk  drive
   and  128K  memory (PC/MS-DOS) or 64K (CP/M) will  run  the  standard
   release.   For  information  about  EASYTYPE  for  other   programs,
   computers, configurations and typesetters, please inquire.  (Contact
   information appears in Section 8.)

          This  manual  covers  two subjects. It  provides  the  mostly
   common-sense   basics   of  preparing  word  processor   files   for
   typesetting.  And, it introduces the powerful features  of  EASYTYPE
   itself,  which permit you to largely ignore conventional needs  when
   preparing word processing files for typesetting.

          Don't  let  the size of EZHELP deter you. EASYTYPE  offers  a
   striking  number  of advanced features you can learn  as  needs  and
   desire dictate. Unless typesetter-specific installation is  required
   (see  below), you actually could begin without EZHELP. As  its  name
   implies, EASYTYPE is very easy to use. But you'll be more productive
   if  you  first  pick up a few tips. And  remember,  EZHELP  is  menu
   driven, so you can find what you want, when you want it.
          You'll find much of this manual is reference material  rather
   than  instructional. If EASYTYPE points out a potential  problem  in
   the original text file, this manual explains what it is, and what to
   do about it.
          So  take  the  time to understand  the  general  content  and
   structure of this help file--time well spent.

          With  EASYTYPE, for the first time ever anyone familiar  with
   word  processing  already  knows how to  prepare  basic  typesetting
   files--without having to learn a single typesetting command or term.
   However, moving beyond some outdated habits as outlined herein makes
   the  typesetting  process easier, faster, more  aesthetic  and  less
   expensive.
          Unlike  alternative approaches to file translation,  EASYTYPE
   is  intelligent.  Once you've used it you won't be  able  to  manage
   without it. Other programs "translate" word processing files  simply
   by removing characters which might confuse the typesetting  program.
   They  also  turn all line endings into "hard" ones,  which  must  be
   individually  removed  by the typesetter.  EASYTYPE  is  intelligent
   enough  to  truly  translate word processing  codes  to  typesetting
   codes.  And  EASYTYPE has the powerful  additional  capabilities  of
   macro  keys.  So if an author wants to do something  of  which  word
   processing  is incapable (size of characters is one  example),  this
   can  be conveyed EXACTLY as the typesetting program expects. Or,  if
   you're  unsure  of all those codes, you can still  use  the  macros.
   Later,  the  typographer can run EASYTYPE or typesetting  editor  to
   make quick, accurate mass substitutions. (EASYTYPE can replace up to
   THIRTEEN macros in a SINGLE pass.) In registered versions, unlimited
   macro Configuration Files can be freely saved to and retrieved  from
   disk, and modified at any time. EASYTYPE offers much more . . .  but
   we'll contain ourselves--for now!

          Note that WordStar and WordPerfect can output numerous  types
   of  file formats. The respective special modes of  EASYTYPE  convert
   the normal TEXT files of these programs. For example, WordStar files
   created in "nondocument" mode and WordPerfect files output with  the
   "DOS" format option--generally unwise for typesetting--are  actually
   ASCII files, covered in Section 2, below. Beginning with Version 5.0
   these  word  processors added limited GRAPHICS  capabilities.  These
   should  be  removed prior to running EASYTYPE.  Otherwise,  EASYTYPE
   must  remove  them  to avoid major  problems  for  typesetting.  But
   results  will  be  unpredictable at best. Instead,  use  the  output
   facilities  of  version  5.0 or later of these  word  processors  to
   generate  files  compatible with their earlier  versions  FIRST.  In
   WordPerfect,  use  control-F5 to enter the "text  in/out"  menu  and
   select  output  to  WP  4.2 format. In  WordStar,  use  the  "Print"
   function, entering "WS4 > FILENAME" at the "Name of printer?" query-
   -replacing FILENAME with a filename of your choice. (Better: Use the
   earlier  versions themselves!) Note that some of the "graphics"  may
   actually  be  inserted "boxed" text. The word  processors  can  drop
   these  during  conversion. Best advice: Insert the "boxed"  copy  as
   ordinary  text and include a "comment to typesetter"  (discussed  in
   next  section) so it can be handled in a normal professional  manner
   in the printer's darkroom later.
          Note  too that "WordStar 2000" files--created by an  entirely
   different program by that name--are ENTIRELY different from WordStar
   files.  As such, they too must be converted before running  EASYTYPE
   or use by a typesetter.
          Thus,  throughout this manual, "WordPerfect"  and  "WordStar"
   refer to normal text files created by programs by the same name.

          EASYTYPE  was created for our own media arts studio  and  its
   clients--a  program  by and for typesetters,  authors,  editors  and
   computerists.  But everyone involved (including the manufacturer  of
   microVISION,  the typesetting interface we use!) thought it  was  so
   valuable  that  we  decided to share its  benefits  with  others  at
   minimal cost.

          Comments  and questions about EASYTYPE and its help file  are
   encouraged. The first person to suggest an idea which is implemented
   will receive a complimentary copy of the enhanced version.

   INSTALLATION

   Please  ensure  you  received all files. (Note to  CP/M  users:  All
   ".EXE" filetypes will be replaced with ".COM".)

   AEHELP.EXE      *Access help files for ALL Advocate products
   AEORDER.EXE      Product descriptions and licensing  form
   AEORDER.HLP      Text file for AEORDER
   AHDINSTL.COM    *Fully-automated hard-disk installation program
   EASYTYPE.FOR    !Brief description of product (suitable for use as a
                    description when uploading to a BBS)
   EASYTYPE.HIS     History of revisions
   EASYTYPE.HLP     Text file you're now reading
   EZ-SHARE.EXE     Main program (includes shareware notice)
    or EASYTYPE.EXE Main program (registered version)
   EZCFG300.EXE    *Converts configuration files from all EASYTYPE
                    formats prior to v. 3.00 to current format
   EZHELP.EXE       Program which displays this text file
   EZINFO.TXT       General systems requirements
   EZMONEY.COM      How to earn Finder's Fees, & distributorship info
   EZSAMPLE.ASC     Sample ASCII file for testing
   EZSAMPLE.WP      Sample WordPerfect file for testing
   EZSAMPLE.WS      Sample WordStar file for testing
   README-T.COM    !Introductory material and/or latest change info
           Notes: * MS-DOS/PC-DOS only
                  + Registration bonus utility (MS-DOS/PC-DOS only)
                  ! Optional file. If present, READ BEFORE INSTALLING
                    THIS PRODUCT IF YOU HAVE NOT YET DONE SO. It may
                    contain important updates to this HELP file.

   IMPORTANT NOTICE TO SHAREWARE-VERSION USERS: Throughout this manual,
   when advised to invoke the program with the name EASYTYPE, please be
   sure to substitute EZ-SHARE instead. The use of different  filenames
   is a safeguard so that after registration you'll have a copy of both
   your  legally  licensed  version and a copy you may  pass  along  to
   others who want to examine the program. When you register, by simply
   copying  all files supplied at that time into the same directory  as
   your  shareware  version your operating  system  will  automatically
   update any files belonging to the shareware version to bring them up
   to date while leaving shareware-specific files untouched.

   If  new  to ordering software, note that  distribution  disks  don't
   contain  "operating system tracks" because of the exceptional  costs
   we would have to pass along. So, to get started, you'll need to make
   copies  of  these  files before using them.  Also,  you'll  want  to
   install the above files to best advantage. It's quick and easy....

                     MS-DOS/PC-DOS Hard Disk Systems
   You  may  either  use  the  accompanying  AHDINSTL.COM  installation
   program (which we STRONGLY recommend) or manually install all files.
   Each is covered separately immediately below.
         AUTOMATIC INSTALLATION: AHDINSTL.COM will do it all for  you--
   copy  all  files to your hard disk, ensure they're  accessible  from
   ANYWHERE  on your system and inform your operating system about  how
   to  use Advocate Enterprises products to maximum potential. All  YOU
   need  to know before using the program are the drive letters of  the
   floppy drive containing your new files and the hard drive from which
   you "boot" (start up) your system each day. (These are almost always
   A: and C:, respectively, which are defaults AHDINSTL uses unless you
   change them.) Also, it is presumed your system already knows how  to
   access  its  COMMAND.COM,  a basic operating  system  program  whose
   services AHDINSTL accesses.
         The   following   text  details  the   tasks   the   automatic
   installation  program performs. If you aren't technically  oriented,
   you  may  want to simply skip this discussion and jump to  the  "All
   Systems"  heading later in this section. Knowledge of the  following
   isn't  essential  except  in  the  unlikely  event  you   experience
   installation difficulty.
         AHDINSTL performs these steps during installation:
         1) It finds (or if necessary creates) a directory named AD_ENT
   off  the  root directory of the drive you indicate  as  your  "boot"
   drive.  (Some Advocate products can provide extra features  if  they
   use this same directory.)
         2) Your AUTOEXEC.BAT file (used by the operating system to set
   up your environment each time you start your computer) is  inspected
   for a "PATH" command. If found, the new AD_ENT directory is appended
   to  it  so Advocate products are accessible from  anywhere  on  your
   system. If no PATH command (or no AUTOEXEC.BAT file) is found, it is
   created.
         3)  If  your AUTOEXEC.BAT file contains no  previous  Advocate
   Enterprises "SET" command, one is added. (Advocate products use this
   to  determine their "home directory." This expands features  without
   affecting other programs in your system.)
         4)  If  you  had a prior AUTOEXEC.BAT file,  it  is  saved  as
   AUTOEXEC.BAK  as a precaution. The only time you're ever  likely  to
   need it is if you have too many or very long prior SET commands.  In
   that  case, the operating system will advise next time you start  up
   that you are "out of environment space." (AHDINSTL uses VERY  little
   environment   block  space.  So  if  you've  reached  your   current
   environment  limit with our installer, you'll soon run into it  with
   another product anyway.) The solution is easy. See the discussion of
   the  CONFIG.SYS  file's  "SHELL" command in  your  operating  system
   manual.  (Contact us as indicated in Section 6 if you  need  further
   help.)
         5) You will be offered the chance to have AHDINSTL  "coldboot"
   (restart)  your computer when it's done. This immediately  activates
   the  changes  the program makes for you;  otherwise,  the  operating
   system won't know about most of them until the next time you restart
   the computer. This is provided as a convenience for you.  IMPORTANT:
   DON'T coldboot if you're currently running other applications in the
   background.  (Coldbooting is equivalent to telling your computer  to
   forget  everything  it's  doing and start over just as  if  you  had
   turned it on for the day.) Now, see "All Systems," below.
         MANUAL  INSTALLATION:  You may simply copy all  files  into  a
   directory  of your choice with a favorite copy program. Just  ensure
   that directory is on your PATH so our products, like others, may  be
   accessed from anywhere on your system. We also strongly urge you  to
   add a "SET" command EARLY in your AUTOEXEC.BAT file so you may  most
   fully  exploit  our product's potential. We assume if  you're  doing
   this  manually you're familiar with how to properly edit that  file.
   The command to add begins with:
   SET ADENT=
   and followed IMMEDIATELY by the drive AND directory containing  your
   new  product. Note that spacing, etc., MUST be in exactly the  above
   format.  The operating system treats them literally. In  particular,
   ensure  there are no trailing spaces after the drive and  directory.
   Example:
   SET ADENT=C:\UTILITIES
   Your  operating system won't offer the benefits of this new  command
   until the NEXT time you restart your computer.
         Most Advocate products work properly without the SET  command,
   but  you  won't  be  able to use AEHELP.EXE,  which  must  know  the
   directory  containing your Advocate files so they may  access  those
   files.  Also, note that without the SET command this program's  help
   program  (which you're now reading) as well as AEORDER  (description
   of products and registration program) can ONLY be accessed FROM  THE
   DIRECTORY WHERE THEY RESIDE.

                          CP/M Hard Disk Systems
   Boot your computer on its hard disk as usual and select a  directory
   for  all  the  new files. Note that the this help  program  and  the
   AEORDER  program expect to find their associated text files  in  the
   same  directory.) Then, copy ALL new files to your hard  disk.  Now,
   see "All Systems," below.

                       All Floppy-Disk-Only Systems
    Format  a  blank disk and add your operating system as  usual,  add
   your favorite file copying utility, and place that disk in drive A:.
   Place  the  new distribution disk in drive B:. Now, copy  all  files
   from B: to A:.
         IMPORTANT NOTE TO MS-DOS/PC-DOS FLOPPY-SYSTEM-ONLY USERS:  See
   the  discussion  on  the AUTOEXEC.BAT "SET"  command  under  "MANUAL
   INSTALLATION,"  above.  The command you'll probably want to  add  to
   your  AUTOEXEC.BAT  file is ONE of the  following,  depending  which
   drive  you expect to use to access Advocate products. (This  command
   isn't essential, but does permit you to use AEHELP.EXE.)
   SET ADENT=A:\
   SET ADENT=B:\

                               All Systems
   Use  ONLY  the  working copies you create. Thwart  Murphy's  Law  by
   safely storing the originals--just in case.

          Some  typesetting  programs  have  unique  requirements   for
   various  things,  such  as  how their  files  store  line  ends  and
   nonprinting "comments." EASYTYPE is distributed with defaults  which
   probably  will work just fine with your typesetter. Try any  of  the
   supplied  test files. Run it through EASYTYPE, then typeset  it.  If
   problems  arise, make a few simple changes discussed in  Section  4.
   After  you've determined any nonstandard needs of  your  typesetter,
   you can save a Configuration File which alters defaults. When  ready
   to  register  your  copy (see the  AEORDER  program),  include  your
   Configuration  File  and we'll send the latest version  of  EASYTYPE
   with YOUR preferences as the defaults.

          NOTE TO MICROVISION USERS: The earliest releases of  EASYTYPE
   were  written especially for your interfaces.  Though  compatibility
   for  most  other typesetters has been added, you will  find  default
   values remain appropriate.

   After familiarizing yourself with this file (and the one with a name
   similar  to  README.COM, if present,  which  contains  late-breaking
   updates  to this manual), follow its procedures and run EASYTYPE  in
   its  WordPerfect mode on EZSAMPLE.WP, an ordinary  WordPerfect  file
   supplied  for your convenience. (Enter any name for the  typesetting
   output  file.) The first time you run EASYTYPE, we suggest you  skip
   all   its  powerful  options.  When  you've  supplied   some   basic
   information  (filenames and such), EASYTYPE will jump to work,  then
   provide its copyrighted file analysis. From the summary, you'll find
   EZSAMPLE.WP was a well-prepared WordPerfect file.
          When  done, select WordStar mode and use EZSAMPLE.WS  as  the
   file.  This  time EASYTYPE's file analysis reveals  serious  errors.
   Though  the test file was created with everyday  WordStar  commands,
   you'll  discover numerous operator errors (such as  unpaired  "bold"
   commands--which  WordStar fails to catch, but not so EASYTYPE!).  On
   most terminals, error messages flash to ensure attention.
          If desired, select Generic/ASCII mode and try EZSAMPLE.ASC.

          We  might note that, while working, EASYTYPE checks the  word
   processing  file  for  clues about whether it  was  created  by  the
   program  you  chose  (WordStar,  WordPerfect,  etc.).  For  outright
   improper files, the analysis screen skips statistics and just  tells
   you it was a bad file. Running EZSAMPLE.WS in EASYTYPE's WordPerfect
   mode provides an example. For less questionable files, the  analysis
   screen  reports all problems encountered. EZSAMPLE.WP in  EASYTYPE's
   WordStar mode provides an example. In all cases, the output file  is
   saved,  with  all  unexpected  characters  flagged  for   typesetter
   attention. EZHELP discusses specifics.

          You  may want to go back and perform similar tests, but  this
   time  "play" with EASYTYPE's main menu functions. After  you've  had
   enough, compare the various files you created with the originals  by
   reading each with a typesetting editor, if possible. (WordStar  also
   can  be used. But if so, ignore the "hyphens" in the  right  margin.
   They  simply  indicate  line endings are  no  longer  what  WordStar
   expects--they  are now in typesetting format!) You'll  be  surprised
   how much EASYTYPE has done for you.

          NOTE: EASYTYPE uses video codes specific to your computer  to
   highlight  and otherwise display information. In the unlikely  event
   you  receive  an inappropriate version, simply return  the  original
   disk  and we'll be happy to replace it. Be sure to tell us the  make
   and  model  of computer. And, if possible, send a photocopy  of  the
   video codes page from your operator's manual.

          We've made sweeping enhancements beginning with version  3.00
   to  accommodate a broad range of available typesetter and  interface
   programs. But there are always enhancements to better interact  with
   such  a variety of software. We'll work with you if you have  ideas,
   run  into  difficulties--whatever.  And, we'll  supply  you  with  a
   complimentary enhanced version containing any of your suggestions we
   implement. This benefits you and all EASYTYPE customers. Help us  to
   serve you better. Contact information is found in Section 8.

   INVOKING EASYTYPE

   You  can  just  type EASYTYPE to begin  normal  use.  However,  when
   registered,  you also can automatically include any of an  unlimited
   number of Configuration Files by typing the name of the file on  the
   command  line. For example, with a Configuration File  named  EZMAIN
   you  would  type EASYTYPE EZMAIN. (As noted previously, be  sure  to
   type  EZ-SHARE  or  EZ-SHARE EZMAIN for  shareware  versions.)  This
   ensures  your  EXACT settings are invoked each time, and  makes  the
   settings within EZMAIN the "defaults" every time you use  EASYTYPE's
   "restore   default  conditions"  function.  You  also  can  load   a
   Configuration File from within EASYTYPE at any time. So, if you have
   different  requirements for different projects, or you use a  single
   copy  of  EASYTYPE with more than one typesetting machine,  you  can
   change  the  configuration  automatically.  (You  also  can   change
   individual  elements of the current configuration at  any  time--and
   create  a  new  Configuration  File, or  replace  the  old  one,  if
   desired.)

          More advanced users may want to create "batch" (MS/PC-DOS) or
   "submit" (CP/M) files to automatically load EASYTYPE and a  specific
   Configuration  File  with  a one-word command.  See  your  operating
   system  manual or computer consultant for details. (Or, if you  have
   registered your EASYTYPE, feel free to contact us.)

          Remember, Configuration Files aren't required. They just  let
   you "fine tune" EASYTYPE's output files to individual preferences.

   ADDITIONAL COMMENTS

   MS-DOS/PC-DOS  users  have received at no charge a  special  utility
   which  takes advantage of some features of their  operating  system.
   AEHELP.EXE  provides a convenient, single access point to  the  main
   help and registration information for ALL of our products which have
   properly been installed according to the above instructions.  AEHELP
   also  assures  you access to all help files from  ANYWHERE  on  your
   system--avoiding  the  need to be in the same directory  as  a  help
   program's  text  file.  (If  you  have  other  Advocate  Enterprises
   products, you may maximize their use simply by placing them in  your
   newly created Advocate directory.)

   MANUAL  CONVENTIONS:  Throughout the manual, reference  is  made  to
   "flag"/"flagged"  and "comment" delimiters. These will be  discussed
   later. As released, these are "<" and ">" for "flag" delimiters  and
   "<*"  and  "*>"  for  comment  delimiters.  We  use  these  defaults
   throughout the manual when referring to flag and comment delimiters.
   If  your  installed version of EASYTYPE substitutes  new  codes  for
   these, make note of this fact when reading related manual text.

        If  you  like EASYTYPE, be sure to inquire  about  EASYDATA,  a
   companion   program   which  converts  DATA-processing   files   for
   typesetting.

          Please  see  AEORDER,  which outlines  the  shareware  review
   process and terms under which EASYTYPE and EASYDATA are distributed.
   It also provides a printable form for registering shareware  copies.
   And note EZMONEY, which describes how you can earn a nice little sum
   by introducing others to the advantages of EASYTYPE and EASYDATA.
~ (Section 2)
                  << THE BASICS FOR WRITERS & EDITORS >>

   EASYTYPE translates virtually anything in word processing files, but
   a few tips make files much more efficient for typesetting.

   LINE ENDINGS: Typesetting will break lines at different places  than
   word processors. So your files should reflect the difference between
   "temporary"  line-ends and those you want the typesetter to be  sure
   to  keep.  EASYTYPE does this for you . . . if you follow  a  simple
   rule:  NEVER  PRESS THE RETURN KEY UNLESS YOU INTEND  A  "PERMANENT"
   LINE END.  This is the way you probably already do it, but it is  so
   critical  it  warrants  emphasis.  Basically,  just  let  your  word
   processor handle line wrapping.
        Each  word processor "hard" line end will be translated into  a
   typesetter  "hard" line end by EASYTYPE. "Soft" line ends (the  kind
   word processors insert for you when you DON'T press RETURN) will  be
   translated  to  a typesetter's "soft" return code.  Usually,  you'll
   only want to press the RETURN key: (1) at the end of paragraphs, (2)
   to  force  a  blank  line WHICH YOU  WANT  TYPESET,  and  (3)  after
   headlines, subheads, etc.

        The above advice works for WordStar and WordPerfect, as well as
   most  other  word  processors which provide an  option  to  generate
   output  files in either of these two leading formats. Things  become
   trickier, however, if you are forced to output to ASCII format  (the
   simplest  of  formats, "understood" by almost any  word  processor).
   Both  the  strength  and  weakness  of  ASCII  files  lie  in  their
   simplicity.  "True" ASCII (some word processors cheat!)  don't  have
   formatting  codes.  They have words and line-end codes.  And  that's
   all.  For our present discussion, the problem is that ALL line  ends
   ("soft"  and  "hard") are IDENTICAL. (Actually, line ends  may  vary
   from one version of ASCII to another--so much for true  universality
   --but they remain consistent within a given editor. But you  needn't
   know the type an editor uses--EASYTYPE figures it out for you!
          How  can  EASYTYPE distinguish hard and soft line  ends  when
   they  are identical? It applies sophisticated algorithms ("rules  of
   logic")  we  developed  for  this  purpose.  Understanding  them  is
   critical if you're preparing ASCII files for typesetting.
          A  line end is considered "hard" (end of paragraph, etc.)  if
   it  is  immediately followed by 1) another line  end  (i.e.,  double
   spacing),  or  2)  a  space or tab  (i.e.,  indented).  It  also  is
   considered "hard" if PRECEDED by another line end (again  indicating
   double  spacing).  IN  ALL  OTHER CASES, (i.e., if  a  line  end  is
   preceded  AND  followed  by anything  else--a  letter,  punctuation,
   etc.),  IT IS TREATED AS "SOFT." This handles the vast  majority  of
   situations.  But  you  COULD run into a problem  if  you  create  an
   itemized list. With ASCII files, your nice aligned list would be run
   together  as  a paragraph unless you take precautions.  There  is  a
   simple solution, and more complex ones.
          The simple solution is to note the position of itemized lists
   in  your main file with "comment to typesetters" (discussed  below),
   then create each list as a separate file. When using EASYTYPE on the
   LIST files only, make a temporary change to how "soft" line ends are
   output.  Simply change the output values for "soft" line ends to  be
   identical  to  what you use for "hard" line ends.  Both  values  are
   displayed  in the special User Environment Menu, reached  by  typing
   "*" from the Main Menu. In other words, you're making all line  ends
   appear  "hard," i.e., not allowing them to wrap during  reformatting
   by the typesetter editor program. (See Section 4 for more details on
   the User Environment Menu.) Just be sure to return the "soft"  line-
   end  values for "nonlist" files when done! (You may manually  return
   such  values to their original state or use the Main  Menu  "Restore
   Default Conditions" function, also discussed in Section 4).
          Note:  "True" ASCII files can be used as list files  by  most
   typesetting  programs without running such files  through  EASYTYPE.
   But  unless you KNOW the file is 100% true ASCII, play it  safe  and
   use EASYTYPE. In our own typesetting, we've had ASCII files  created
   by  the most popular word processors which contained a hidden  "bad"
   character.  Our typesetting editor program readily accepted  it  and
   sent  it out to the typesetter--which stopped COLD.  EASYTYPE  NEVER
   places  anything in the output file until completely  inspected  and
   approved.
          But  . . . if you're stuck with lists embedded  within  ASCII
   files containing normal (paragraph) text--perhaps provided that  way
   by  others, you can still solve tricky reformatting problems with  a
   little creativity. Here are some good approaches for starters:
     1) Indent your list (like this one).
     2) Or, double-space it.
     3) You could insert an EASYTYPE macro character at the beginning
        (or end) of each list item so EASYTYPE globally replaces it
        with a typesetting hard return. (The soft return disappears
        during typesetting paragraph reformatting.)
     4) You could insert a "comment to typesetter" (discussed later) to
        tell the typesetter to insert hard line ends.

   HYPHENATION:  Like  line endings, the general rule is to  avoid  all
   hyphens  except  those  you want  "permanently"  retained.  EASYTYPE
   understands  and translates "discretionary" hyphens in WordStar  and
   WordPerfect files.
          If  your word processor is installed with "hyphenation  help"
   turned  on, we recommend that you either change it,  or  temporarily
   turn it OFF when creating files for typesetting. (Note: If your word
   processor  is  other than WordStar or WordPerfect and  you  plan  to
   output  to  one  of  those  formats,  you  should  test  to   ensure
   discretionary  hyphens  are handled properly. This is one  of  those
   more  "esoteric"  areas which translators other  than  EASYTYPE  can
   miss.  And  if  you plan to convert to  ASCII,  avoid  discretionary
   hyphens at all costs. ASCII has NO such code, so either you'll  lose
   the  discretionary hyphens (which is OK--but then why bother in  the
   first place?) or they'll be converted to mandatory hyphens (ugh!!!).

   WORD  PROCESSING  LINE JUSTIFICATION: Simply put: TURN IT  OFF.  The
   codes used for word processor justification are highly  incompatible
   with  typesetting, so EASYTYPE must mark them for  the  typesetter--
   much needless work. Use "comments to typesetter" instead.

   WHITE  SPACE:  One reason typesetting is so superior  to  all  other
   forms of output is the way it handles "white space"--that is, things
   other than printable characters. Justification (above) creates white
   space--extra space between words. So do tabs, the spacebar--and  use
   of columnar mode in later WordStar versions. Typesetting gains  much
   of  its  beauty  by the unique ways  it  handles  space--ways  quite
   dissimilar  to word processing. In general, EASYTYPE must undo  what
   word  processors inflict upon typesetting-bound files.  WordStar  is
   particularly  bad  about  this, as it uses the  identical  code  for
   nearly  every  kind of white space. EASYTYPE again  must  mark  many
   problem areas for the professional attention of the typesetter. It's
   therefore  better  not to create the problems  in the  first  place.
   Some tips:
          First,  use one and only one space between words,  sentences,
   etc.  (Forget  the outdated typewriter "rule"  about  double-spacing
   between  sentences.  This can even cause imperfections  in  ordinary
   computer output; but for typesetting, it's a real no-no.)
          Secondly, it's best to avoid the TAB key. In word processing,
   TABs  might  be used to indent paragraphs, align  tables  and  other
   purposes.  But  each of these is handled in ENTIRELY  separate  ways
   from  each  other  in  the  typesetting  environment,  so  you  must
   differentiate between them. (In general, EASYTYPE must mark them for
   your  graphic arts pro to attempt to figure out what you  meant.  If
   you  think  you must use TABs (such as for  columns),  consult  your
   typesetter  first--or  leave a "comment  to  typesetter"  (discussed
   below) to describe what you intend.
          "Newsletter-style" columnar text deserves special  attention.
   For  typesetting to properly handle such word processing  files,  EZ
   must  first  "decolumnize" the text. WordPerfect  users  may  safely
   prepare  text  in columns if they really desire, and  EASYTYPE  will
   undo  the columns for you (even if you switch in and out  of  column
   mode!). But columns take a little longer to process, create a little
   extra  work for the typesetter (because of some special codes  which
   WordPerfect  uses and EASYTYPE must pass along)--and in  any  event,
   there's no net benefit. So why bother? WordStar and many other  word
   processors,  however,  handle matters  quite  differently,  creating
   major  problems  or  worse for typesetting.  This  is  definitely  a
   subject for Beyond the Basics--the next chapter!
          For  paragraph  indentation, you normally will  NOT  want  to
   indent  during  file preparation. Instead, an EASYTYPE  Option  Menu
   function  can  globally and automatically insert a fixed  amount  of
   space after all hard returns. Or, you could insert an EASYTYPE macro
   character  for each indentation. Later, you or your  typesetter  can
   globally replace them with a typesetting code for a selected  amount
   of  space. (EASYTYPE Options Menus and macro keys are  discussed  in
   Section  4.) Optionally, you can leave a "comment to typesetter"  to
   ask  your  graphic arts pro to add an aesthetically  pleasing  fixed
   space  for indentation. If you use TABs for  paragraph  indentation,
   EASYTYPE simply marks them so your graphic arts pro can convert each
   one manually.
          WordStar  user  who use "nonbreak" spaces  (^PO)  should  see
   Section 4.
          Note  that there's no need to use WordStar's ^OL  command  to
   change the left margin. In typesetting, page or columnar positioning
   is  done  AFTER  text  is set on film.  In  fact,  left  to  itself,
   WordStar's special codes for left margins would create havoc  during
   typesetting.  So EASYTYPE politely removes them. The net  result  of
   using the ^OL command for typesetting files is wasted disk space and
   slower processing.

   BOLD,  ITALIC, ETC.: In word processing, codes toggle each of  these
   functions  on,  then  off. Typesetting is  different.  It  has  many
   typefaces from which to choose, each identified by a code.  Example:
   You  might select typeface #3 for Bold, then go to typeface  #2  for
   italic--or maybe typeface #8 for a completely different "family"  of
   type (i.e., related typefaces). EASYTYPE helps make this transition.
          For  your  main  "family," just type  as  usual--use  regular
   typing  for "normal," and your word processor's  built-in  functions
   for  underscore ("italic") and bold. Any other options you may  have
   (e.g., "double-strike" in WordStar) can be used for any purpose  you
   wish  (maybe  "bold italic"--or perhaps something  quite  different,
   such  as  a  size  of type). Just be sure to  leave  a  "comment  to
   typesetter"  to communicate your intent, or better,  use  EASYTYPE's
   Option  Menu  to  globally  replace  these  codes  with  typesetting
   counterparts.
          For additional typefaces, use macro keys (Sections 3 and  4).
   You  simply  enter a single character which later will  be  globally
   replaced with a full string of codes.
          IMPORTANT  NOTE: In WordStar, ^PB^PSThis  Phrase^PS^PB  would
   print "This Phrase" in BOTH bold and "italic" (underscore). This  is
   because each of these printer functions is independent of the other.
   Not  so  in  typesetting! Typesetting  offers  a  separate,  genuine
   typeface  for every function--"normal," italic, bold,  whatever.  In
   the above example, thus This Phrase would actually be only in italic
   because you changed from "normal" to bold to italic THEN printed the
   phrase, then returned to normal! If you want "bold italic," you must
   explicitly  request  it  with an  otherwise  unused  word  processor
   printer  code,  or  better,  an  EASYTYPE  macro  (or  "comment   to
   typesetter" for someone else to fix).
          While  we're at it: Only capitalize what you really  want  in
   caps.  Don't  use caps to convey "bold." An  advantage  of  directly
   submitting  disk files for typesetting is that YOU retain  control--
   and  at a significant savings in cost; but this also means you  must
   say what you intend. YOU are responsible for content--so be precise.

   QUOTATION MARKS: Computers use the same symbol to mark the beginning
   and  end of quotes. But as you probably know, one of  the  aesthetic
   elements in typesetting is use of different sets of marks on  either
   side  of  quotes.  We gave EASYTYPE a special  algorithm  ("rule  of
   logic"--remember?)  to  determine whether a "begin"  or  "end"  code
   should replace the computer code in any given situation.
          Unfortunately,  this logic can't extend to the  single  quote
   marks  used for "quotes within quotes" because, while computers  use
   the same symbol for "begin" and "end" single quotes and  typesetting
   doesn't,  both  use the single "end" mark for  apostrophes  too.  So
   you'll  need to either insert "comments to typesetters," or  better,
   assign EASYTYPE macro keys.

   WORDSTAR  "DOT  COMMANDS": Your word processor uses these  both  for
   format  commands  and  "comments" to remind  yourself  of  something
   later.  EASYTYPE marks all of these as "comments to  typesetter"  so
   they  won't be typeset. However, remember that your  typesetter  may
   not  be  well-versed  in WordStar. So you should  explain  any  "dot
   command"  meanings  in  English, or remove them  if  irrelevant  for
   typesetting.

   MATH  FUNCTIONS: Some word processor versions can  perform  subtotal
   and other math functions, displaying or printing the results in  the
   appropriate  places in text. These data generally are NOT stored  in
   the  file, and instead are calculated ONLY when the word  processing
   program is active. So your totals and so forth WILL NOT BE AVAILABLE
   TO  THE  TYPESETTER. The best solution is to avoid  these  functions
   altogether and instead manually insert totals and the like. If  this
   isn't  feasible,  EASYTYPE will insert a warning code (see  list  in
   Section  6) to the typesetter. It is the author's responsibility  to
   communicate  further  with the typesetter, either by a  "comment  to
   typesetter"  or  by providing a computer-printed copy  of  the  file
   along with a note directing the typesetter to problem areas.

   "COMMENTS TO TYPESETTERS": You can convey comments and  instructions
   to  your  graphic  arts  pro in two ways.  You  can  embed  comments
   directly  within  text by placing them between "flag"  or  "comment"
   delimiters (environment-specific codes described in Section 4).  For
   example: <LIKE THIS> (flagged--the default and preferred) or  <*LIKE
   THIS*>  (comment).  Or,  with WordStar, you  can  use  its  built-in
   "comment"  function,  which EASYTYPE understands  and  automatically
   places within delimiters for you to mark for your typesetter. Simply
   begin  a  comment line with ".IG" or ".." at the VERY left  edge  of
   your  screen. (If your comment is longer than one line,  begin  each
   line the same way or part of your comment will be typeset!)
~ (Section 3)
                         << BEYOND THE BASICS >>

   In  theory,  you  can  submit a word  processing  file  which,  with
   EASYTYPE, can be prepared for final output with a SINGLE  formatting
   command by your typesetter (to calculate output line breaks). That's
   theory. In practice, a few more considerations are involved. Section
   2  outlined  the  basics of greatly reducing  typesetting  time  and
   costs.  But  if you choose, you can save even more . . .  and  as  a
   bonus enhance your typesetting.

          The  first  Beyond the Basics advice: COMMUNICATE  WITH  YOUR
   TYPESETTER  EARLY IF FILES WILL CONTAIN ANYTHING  EXCEPT  "STRAIGHT"
   TEXT. For example, your graphic arts pro probably will request  that
   you  submit many types of charts, tables, etc., as  separate  files,
   with main-file "comments to typesetter" like: <INSERT FILE 2  HERE>.
   At a minimum, communication saves time and money. At worst,  without
   advance planning your typesetter may have to re-enter text.
          Secondly,  if  you really want to  approach  the  theoretical
   "ready-to-use"  file,  you  can insert some or all  of  the  special
   typesetting codes which otherwise would be left to your graphic arts
   pro. This of course offers further time and cost benefits, but  also
   provides  much greater control of the final product.  For  "straight
   text,"  you'll need fairly few codes, most of which can be  included
   in a single line at the head of a file. (That line may be added with
   an  EASYTYPE Options Menus function. For repetitive  projects,  with
   registered  copies of EASYTYPE these and all options can easily  and
   permanently be saved to disk and retrieved later!) But you might  be
   willing  to add a few more. Contact your typesetter if you  plan  to
   work  regularly with him or her. If so, investing a little  time  to
   develop  a "style sheet" of codes unique to your needs benefit  both
   of  you.  Your  typesetter may even already have or  be  willing  to
   prepare Configuration Files for you.
          EASYTYPE's unique macro keys make inserting typesetting codes
   a  snap.  Maybe  you  don't  want  to  memorize,  let  alone   type,
   <SS10><SF7>  for  every subhead in your book-length  manuscript.  Or
   maybe  you haven't even selected typefaces so simply can't know  the
   codes.  No problem! Just use an EASYTYPE macro character  which  you
   won't  use in the book (such as the "|" character). Later,  EASYTYPE
   can automatically and simultaneously replace all macros with desired
   codes  while  translating your file. As a bonus, by  using  EASYTYPE
   macros you can redefine functions over and over, quickly and easily,
   by simply having EASYTYPE reformat your original file. You even  can
   use it to replace TEXT--or just as easily a combination of text  AND
   codes! (See Section 6 for a complete list of macro keys.)
~ (Section 4)
                    << EASYTYPE RUN-TIME FUNCTIONS >>

   EASYTYPE can translate your word processing file into a  typesetting
   file  simply by specifying a name for both and indicating  which  of
   three modes (e.g., WordPerfect) applies. But what makes the  program
   truly excel is its ability to perform many time-consuming and error-
   prone steps quickly and reliably through selected options. Below are
   the  EASYTYPE options and their defaults (i.e., what happens if  you
   don't   change  them).  EASYTYPE  performs  these   functions   more
   effectively   than  other  programs  in  the   word   processing-to-
   typesetting process. Be sure to contact your typesetter about proper
   settings for a given task before using them.
          When  using other-than-default settings, we urge you to  save
   them  to a Configuration File (described shortly), then submit  that
   file along with word processor and typesetting files for  typesetter
   review.

   MAIN MENU FUNCTIONS

   FUNCTIONS  1  AND 2: Move you to EASYTYPE  Options  Menus  described
   below.

   FUNCTION 3: Provides an assured way to remove any modifications  you
   may  have made to default settings. Afterward, you can be  confident
   you have returned EASYTYPE to the same conditions as when you  first
   entered  the  program (or last retrieved a  Configuration  File,  if
   you've  done so). You needn't worry about having forgotten to  reset
   something.

   FUNCTIONS  4 AND 5: Use these, respectively, to save  configurations
   for   future  use  and  retrieve  previous   configurations.   (Your
   configurations  are stored in permanent disk files.) You can  freely
   modify   retrieved   settings  and,  if  desired,  store   the   new
   configuration  too.  There is no practical limit to  the  number  of
   Configuration Files. (Note: A EASYTYPE registration license must  be
   obtained before Configuration Files can be retrieved.)

   FUNCTION  6:  Lets  you switch  between  WordStar,  WordPerfect  and
   Generic/ASCII mode. If you change between Generic/ASCII and  another
   mode, the setting of Function 7 automatically changes too. (Note the
   Section 1 discussion on the meaning of "WordStar" and "WordPerfect."
   Use  the normal TEXT-creating features these top two word  processor
   formats  offer  and  EASYTYPE so faithfully taps.  But  if  WordStar
   "nondocument"  or  WordPerfect "DOS" format can't  be  avoided,  use
   EASYTYPE's Generic/ASCII mode.)

   FUNCTION  7: WordStar and WordPerfect (but not ASCII) files  contain
   an  amazing  variety of formatting codes. Where  possible,  EASYTYPE
   quietly  changes  them  to typesetting  equivalents.  But  when  not
   practical,  this  function  lets  you specify  HOW  such  codes  are
   handled.  The  default  is "FLAGGED," which  means  that  when  your
   typesetter  reformats your EASYTYPE file, each code  which  requires
   operator decision will halt reformatting at the code. With  Function
   7, you can tell EASYTYPE to switch to "COMMENT" reporting format. In
   this  mode,  formatting codes are inserted in such a way  that  they
   will NOT affect typesetting. They will, however, remain in the  file
   as  information-only  codes  which  the  typesetter  can  choose  to
   consider or ignore. (Note: "flagged" and "comment" codes vary  among
   typesetters, and may require one-time installation with Function "*"
   below.)
          Unless you are an experienced user or have been advised to do
   otherwise,  it's  best  to use the default FLAGGED  mode.  But  with
   experience, you may find that in some situations such codes are more
   of  a distraction than a help, and so may prefer COMMENT mode.  What
   are  factors  which might affect this  decision?  Purely  "straight"
   files  can  benefit from COMMENT mode, freeing the  typesetter  from
   deleting  codes.  The same may be true when the  author  supplies  a
   sample  printout  as  a  guide for  the  typesetter.  Lastly,  since
   WordPerfect  uses codes to indicate virtually ALL of  its  functions
   while  WordStar more often performs requested functions directly  on
   the  file's  text, WordStar tends to have less embedded  codes  (and
   when  it does, they tend to be more important to know). So  when  we
   use  EASYTYPE  ourselves,  we tend to use  COMMENT  more  often  for
   WordPerfect  files, less often for WordStar files. You'll  soon  the
   better choice for your needs.

   FUNCTIONS  8  AND  9:  Use to  specify,  respectively,  input  (word
   processor) and output (typesetter) filenames. Note that input  files
   larger  than approximately 20K (which can create problems  for  some
   typesetters,  including microVISION)) are accompanied by a  FLASHING
   filesize  display.  You may want to divide them into  smaller  files
   before using EASYTYPE.

   FUNCTION B: Begins conversion.

   FUNCTION  "*": We made this a little harder to invoke (you must  use
   the shift key) so you're less likely to press it unintentionally. It
   provides  several user-specific functions you're likely to  have  to
   use  only once, if at all, to install a few options unique  to  your
   typesetter as described under USER-SPECIFIC MENU, below.

   FUNCTION  Q: Quits EASYTYPE. But before doing so, if you  have  used
   options  settings  other than defaults, you may first want  to  save
   them to a Configuration File with Function 4 for future retrieval.

   OPTIONS MENU 1

   Choosing Function 1 from the Main Menu moves you to Options Menu  1.
   Once here, you can change how EASYTYPE translates or inserts certain
   codes and performs some other tasks. Choices available in this  menu
   vary  according to the mode (WordStar, etc.) selected from the  main
   menu.  (Don't  worry, EASYTYPE won't let you  access  options  which
   don't  currently apply.) The first three options below apply to  all
   modes.  Others  apply  only to  WordStar,  WordPerfect--or  both--as
   indicated.

   FIRST  LINE INSERT: Permits you to add a short, one-line  insert  at
   the  head  of  the  output file. It may  be  a  simple  "comment  to
   typesetter,"  or  codes used to initiate typesetting  (line  length,
   size  of  type, etc.). You can enter these with EASYTYPE,  or  leave
   them  for your typesetter to insert. If you use the same format  for
   many  files,  you should obtain these codes from your  graphic  arts
   pro. By entering them ONCE, you can insert them in successive files,
   --and  save  them  for  future  files  after  registering  EASYTYPE.
   Default: none.

   PRECEDE HARD RETURN: In most cases, you'll want text on lines  which
   were ended by physically pressing RETURN to be "quad left," that is,
   with all unused space to the right--like this line.
        Word  processors more or less demand this;  typesetters  don't,
   permitting  greater  creativity  for some  purposes.  Without  "quad
   left,"  the last lines of paragraphs will often look something  like
   this                           one                             here.
          Left  to default operation, EASYTYPE adds a "quad left"  code
   before each HARD RETURN. If you plan something unusual, contact your
   typesetter for appropriate codes.

   FOLLOW HARD RETURN: EASYTYPE's default is "none," meaning nothing is
   inserted after a hard RETURN. Often, you won't want to change  this.
   But  maybe almost all of your file will be indented. Or,  maybe  you
   want  to add a little more than normal space between paragraphs  and
   can't  indicate  this  with a word processor. An  alternative  to  a
   "comment  to typesetter" is to add codes obtained from your  graphic
   arts pro with this option.

   MAIN TYPEFACE (WordStar and WordPerfect): This code will be inserted
   after BOLD, ITALIC, etc., has been used and text is returning to the
   normal typeface. Default: <MAIN>.

   BOLD & ITALIC (WordStar and WordPerfect): Typesetting uses  separate
   codes  for  beginning  and ending each of  thousands  of  typefaces.
   WordPerfect uses a fixed set of codes to mark the beginning of  bold
   text,  the  end of bold, the beginning of  underscore  ("italic"  in
   typesetting) and the end of underscore. It doesn't have a  different
   code  for, say, the beginning of bold in one typeface and bold in  a
   second  typeface. By contrast, WordStar uses just ONE code for  both
   beginning  AND  ending bold, and a second for beginning  and  ending
   underscore.  EASYTYPE handles the details for correctly marking  the
   beginning  and  end  of bold or underscored text.  But  because,  by
   itself,  it  has  no way of knowing the PRECISE codes  for  a  given
   typeface,  EASYTYPE can benefit from a little (optional) help.  With
   options  for  each of your word processor's printer codes,  you  can
   define  the  corresponding typesetter codes with the  help  of  your
   graphic arts pro. Or, you can leave the defaults for your typesetter
   to  replace  later.  The defaults are <BOLD> for  "start  bold"  and
   <ITAL> for "start italic." <MAIN> is the default for both "end bold"
   and "end italic," in each case returning to the basic typeface.

   'DOUBLE-STRIKE'  (WordStar  only): A second type of  bold  for  word
   processing,  for typesetting you can assign any additional  typeface
   (or  other  characteristic)  desired. Defaults are  <DS>  to  "start
   double-strike" and, of course, <MAIN> for "end double-strike."

   'NONBREAK' SPACE TOGGLE (WordStar only): Involves a code seldom used
   by WordStar authors, but EASYTYPE is ready for it. This option  also
   is  handled differently from others in that it is a  "toggle."  That
   is, you select one of two choices rather than entering characters.
          In  WordStar, a ^PO code placed between two words  tells  the
   computer  and  its printer to never separate them at the  end  of  a
   line.  Typesetting  has no direct equivalent, so EASYTYPE  lets  you
   either  translate all "nonbreak" spaces into normal spaces  or  mark
   them for your typesetter. Default: <NB> to flag them for typesetter.

   FOOTNOTE  FIRST LINE & ENDNOTE FIRST LINE (WordPerfect  only):  Just
   like the main FIRST LINE INSERT, above, except placed at the head of
   all  footnotes  and endnotes, respectively,  which  EASYTYPE  groups
   together for your typesetter. Default: none.

   BEGINNING  FOOTNOTE NUMBER & BEGINNING ENDNOTE  NUMBER  (WordPerfect
   only): WordPerfect lets you create very large files, with  footnotes
   which  will be printed at the end of the page on which the  footnote
   number appears and endnotes which are gathered and placed at the end
   of  the  document.  But this creates  problems  in  the  typesetting
   environment.
          The  first  problem  is that  typesetting  often  can't,  and
   probably shouldn't, work with very large files. (It's not even often
   wise in word processing. But imagine the time and costs of a  simple
   error  at the head of a typesetting file which results in the  wrong
   typeface throughout the file.) But if you use WordPerfect to  divide
   a  file, you may find that the first "note" in every file  has  been
   renumbered as "1"! So EASYTYPE lets you specify the number at  which
   to  begin  a file's footnotes and endnotes. And after  converting  a
   file,  EASYTYPE  informs you of the total number  of  footnotes  and
   endnotes.  So  if  you  run another, related  file,  you  can  start
   numbering where the previous file left off. IMPORTANT: Both  numbers
   are reset to the default of "1" after every file so you won't forget
   to do so between unrelated files.
          Another  problem  is  that, until later  in  the  typesetting
   process,  the place where a page ends normally isn't known. So  it's
   necessary  that  all  footnotes  and endnotes  be  gathered  in  one
   location for later positioning. EASYTYPE does this for you,  placing
   all  footnotes  after  all regular text. This  is  followed  by  all
   endnotes.

   PRECEDE FOOTNOTE, FOLLOW FOOTNOTE, PRECEDE ENDNOTE & FOLLOW  ENDNOTE
   (WordPerfect  only): Defaults: none. These options are available  if
   you  need to insert codes before and after footnote NUMBERS  in  the
   main text to obtain superscripts. "Precede" codes are placed  before
   EACH  digit  of  a number; "follow" codes only  after  the  COMPLETE
   number--as  expected by most typesetters. Example,  for  microVISION
   users processing a footnote numbered 12, setting Precede Footnote to
   "<SF5>@"  and  Follow  Footnote  to  "<SF1>"  might  be   desirable,
   resulting in a result of <SF5>@1<SF5>@2<SF1>. (Isn't it nice NOT  to
   have to enter all that every time now that you're using EASYTYPE?!)

   OPTIONS MENU 2

   This  menu lists 13 characters found on most computer keyboards  but
   which don't exist on all common typesetting fonts or require varying
   keystrokes/codes  to access them. If you by chance use any of  these
   somewhat  uncommon  characters  (also listed  in  Section  6),  your
   typesetter  can  tell you if they exist in the  typeface  you'll  be
   using  and,  if  so, what codes can be  substituted  for  them  with
   EASYTYPE.
          Any of these characters which you don't use for ordinary text
   is available as a EASYTYPE "macro" substitution character, described
   earlier in this section and in Beyond the Basics (Section 3).

   USER-SPECIFIC ENVIRONMENT MENU

    The choices listed on this menu may never be needed--or just  once,
   if  you  haven't  yet registered your copy of  EASYTYPE.  Use  these
   options  ONLY if you find it necessary after discovering  that  your
   typesetter  has uncommon needs. Then, find your defaults, save  them
   to  an  EASYTYPE  Configuration  File and send it  to  us  when  you
   register.  Your  registered copy contains your  unique  preferences,
   based  upon  the file you send. If you can't  find  the  appropriate
   setting  and your typesetting manufacturer won't help,  contact  us.
   We'll assist. Options from this menu are as follows.

   SOFT  LINE END: The code your typesetter stores at the end of  lines
   capable of being "wrapped" around when you edit a  file--essentially
   lines within paragraphs. Because these codes can't be directly typed
   like a letter or number, you must enter the "ASCII decimal"  numbers
   equivalent  to  your  codes. (A string of either one  or  two  codes
   allowed.) Default: 141.

   HARD LINE END: For ends of paragraphs, etc., where a line end is  to
   be  "permanent."  Use  one or two ASCII decimal  numbers  here  too.
   Default: 13.

   LEFT COMMENT & RIGHT COMMENT: Like WordStar, many typesetters permit
   nonprinting  comments  within texts as reminders  to  the  operator.
   Enter  the actual characters for such here, if available and  known.
   Otherwise,  we recommend you leave these to their defaults  of  "<*"
   and  "*>" respectively. EASYTYPE needs SOME kind of "comment"  codes
   to  use  when reporting problems which might be  found  within  word
   processor  files,  so we urge you not to make "comment"  codes  into
   blank (nonexisting) codes.

   LEFT  FLAGGED  & RIGHT FLAGGED: Similar to "comment"  codes,  above,
   except these should be some kind of "illegal" codes which will cause
   your  typesetter's  editor  to catch them  while  reformatting  line
   lengths. If in doubt, we again urge that you retain the defaults  of
   "<" and ">" until you find a need to change them.

   LEFT QUOTE & RIGHT QUOTE MARKS: Word processors use the same symbols
   to begin and end quotes. Typesetting uses the real (and  different!)
   symbols  for each. Your typesetter may have special indicators,  but
   EASYTYPE  defaults translate opening (left) quotes to  two  computer
   quote marks ("") and closing (right) quotes to two apostrophes (''),
   as often expected by typesetters prior to final output. Pay  special
   attention to this and the next one!

   DISCRETIONARY HYPHEN: Your typesetter probably has a way to indicate
   a  "discretionary"  hyphen--i.e., one which only is  typeset  if  it
   happens to come at the end of a line after reformatting. Insert your
   code here. Default is the often-expected equal sign (=).

   'EN'-SPACE:  This is a fixed unit of space in typesetters, equal  to
   the width of the letter N and commonly of numerals. EASYTYPE uses it
   between a footnote number and the beginning of the footnote text for
   professional  alignment.  If you know the code for an  actual  fixed
   space  ('en'  space  or otherwise) which you want to  use  for  this
   purpose,  enter it here. Otherwise, type the literal word SPACE  and
   EASYTYPE  will insert an ordinary, variable-width space. In no  case
   should you leave this entirely blank.
~ (Section 5)
                          << FOR TYPESETTERS >>

   At long last, a program--EASYTYPE--directly converts word  processor
   files  into typesetting files. Best of all,  client-entered  "bold,"
   "italic,"  and other codes can be entered in normal  word  processor
   fashion your client already knows, yet are faithfully translated and
   retained.  And "hard" line ends remain hard while "soft"  line  ends
   remain  soft--so  typesetters  can  reformat  paragraphs  of   these
   "foreign"  files just like their own! Even codes not provided  by  a
   word  processor  can be added automatically during  conversion  with
   EASYTYPE's  unique  macro  key function.  Equally  helpful  is  that
   details  such  as  inserting quad-left codes  before  hard  carriage
   returns  and alternating typesetting beginning and ending  quotation
   marks  are  done for you. EASYTYPE cuts editing (and  errors)  to  a
   fraction of what they were!

          Be sure to familiarize yourself with the help file to  better
   understand  the process. Particularly note the next  section,  which
   details  the output of EASYTYPE and explains warning messages  about
   possible errors in the original word processing files. The help file
   suggests  tips you can pass along to clients to benefit both of  you
   and  details  EASYTYPE  Options Menus  and  other  functions,  which
   eliminate  major  editing tasks. (You might even  consider  a  short
   public-service seminar, from which everyone benefits!)

          We'll  walk through a step-by-step example in a  moment.  But
   first we'd like you to know you can either run EASYTYPE yourself, or
   with  a  resale  license, profitably distribute it  to  clients  and
   others.
          You and your clients will be amazed at how fast you turn jobs
   around because of the large saving in time.

          So  .  . . let's follow a typical file after  translation  by
   EASYTYPE. We'll use the microVISION typesetting interface system  to
   illustrate.  Substitute  parallel  procedures as  needed  for  other
   systems.
          Invoke  your  typesetting  editor normally.  If  your  client
   hasn't  entered  line measure, etc., with the EASYTYPE  Option  Menu
   function  for  that  purpose, do so as usual.  Prepare  any  desired
   macros--see  "tip"  below. (You won't need one for  quad-left  codes
   though--EASYTYPE  already has inserted them for you) In most  cases,
   you'll only need font-change and size-change format keys.
          You're  now  ready  to  zip  through  the  file,  adding  any
   typesetting  commands  not entered by your client. Simply  use  your
   editor's  reformatting function. In most cases, the cursor will  fly
   through  the  file,  reformatting to  typesetter  line  measure  and
   pausing  only at anything which may require attention. EASYTYPE  has
   marked  such events by user-set "flag" delimiters  indicators.  Just
   edit as needed, then resume reformatting.

   TIP:  In  microVISION, set up macro keys with  desired  codes,  each
   followed  by ^T^Q^Q0^N^B, which (after inserting your main code)  is
   its  way  of  saying "delete the rest of the  'flagged'  code,  then
   resume  paragraph reformatting until encountering another  'flagged'
   code."  Example: If your client hasn't entered font codes  for  bold
   with EASYTYPE, the default you'll find is <BOLD> for "turn on  bold"
   and  <MAIN> for "turn off bold" (i.e., return to regular font).  For
   the Comp IV typesetter and typical film strip, microVISION codes for
   these  functions, respectively, might be <SF3> and <SF1>. So,  let's
   say  microVISION, while reformatting, pauses at <BOLD>.  You  should
   have  a  macro  containing: SF3>^T^Q^Q0^N^B. (Note  absence  of  the
   opening  "<".)  By pressing it, you first  insert  the  microVISION-
   specific  code, then delete EASYTYPE's temporary code  and  continue
   reformatting  to the next flag code (probably <MAIN> to  end  bold).
   There,  use your SF1>^T^Q^Q0^N^B macro to return  to  regular-weight
   face.  (An alternative is to set one macro for ^T^Q^Q0^N^B  and  set
   all  others  without it, in which case you of course would  use  two
   macros  per substitution.) Note that, for word processors, bold  and
   italic are independent functions. So you MIGHT discover <ITALIC> and
   <BOLD>  both appearing before two <MAIN> codes. If so,  your  client
   probably wants a bold italic face. In that case, you'll have to  use
   your expertise to perform a little extra surgery based upon judgment
   of your client's intentions.

          Soon you'll be preparing most files for typesetter output  in
   a fraction of the time formerly required. . . .If you discover ideas
   for  enhancements  to  EASYTYPE, let us know. If  you're  the  first
   to  suggest an idea we use, you will receive a copy of the  enhanced
   version. Contact us too about programs for other applications,  such
   as  EASYDATA,  a companion program  which  converts  DATA-processing
   files for typesetting. See Section 8 for address/phone.

          CONCLUDING  THOUGHT: If your client already ran EASYTYPE  and
   saved  options settings to a disk Configuration File,  request  that
   file  as  well  as  the  EASYTYPE  output  file  and  original  word
   processing file. If you need global changes to the file, you'll find
   it's easy. Just run EASYTYPE with your client's Configuration  File,
   change  any desired settings and you'll have an updated  typesetting
   file in seconds!
~(Section 6)
           << EASYTYPE TRANSLATION ROUTINES & FILE ANALYSIS >>

   This section covers two related subjects: details about how EASYTYPE
   translates many specific codes; and the summary file-analysis screen
   (plus warning messages, if any) displayed after translation.
          Below,  EZ  refers  to  EASYTYPE,  WS  to  WordStar,  WP   to
   WordPerfect and ASCII to Generic/ASCII. All sections apply to WS, WP
   and  ASCII  modes unless otherwise indicated.  EZ's  default  "flag"
   delimiters  ("<"  and  ">") are used below. They,  as  well  as  the
   specific translation codes discussed, are user-configurable.

   TRANSLATION CODES

                                  <BOLD>
   EZ's  default for "start bold." If EZ's Options Menu 1 (see  Section
   4)  is used, the actual typesetting code for a specific  typesetting
   environment is inserted instead. If the number of <BOLD> and  <MAIN>
   ("end  bold"--see  below) codes in a file don't match,  it  probably
   indicates an author error. So EZ issues a warning (see below).

                                  <ITAL>
   Similar to bold, this code identifies "start italic." (Italic is the
   typesetting equivalent to computer underscoring.)

                                   <DS>
   (WS only) A "less bold than bold" option called "double-strike." For
   typesetting  files,  this  can be used for  any  typeface  or  other
   function the author wishes--just leave a "comment to typesetter"  to
   explain  the  intention  if  EZ's default  rather  than  a  specific
   typesetting code is used.

                                  <MAIN>
   Indicates  the author used the word processor's command to turn  off
   bold, italic or double-strike. (The same code is used to end each of
   these  functions,  as  they always mean  "return  to  regular-weight
   face.")  If  the author FORGOT to turn off one of  these  functions,
   EASYTYPE issues a warning message on its file analysis screen.

            <{> <|> <}> <~> <#> <%> <+> <=> <@> <\> <^> <_><`>
   Some  typefaces  don't offer certain of these computer  symbols,  or
   offer  them  with varying "shifted" keys. So EZ places  them  within
   "flag delimiters for the attention of the typesetter. Authors should
   consult  their typesetters prior to using these symbols  in  regular
   text. It may affect typeface selection. Or, you may prefer alternate
   approaches (e.g., typing "control-B" instead of "^B"). Best of  all,
   if you want to use one of these characters and it DOES exist in  the
   typeface  to be used, you can use it and let EZ globally replace  it
   with the corresponding typesetting code! EZ indicates how many  such
   "unexpected" symbols are encountered.
          Any  of  these symbols can be used as an EZ  macro  key.  For
   example, "|" might be used to mean 24-point Souvenir Medium type. By
   substituting the exact code the typesetter expects for this  purpose
   with  Options Menu 2, every occurrence of "|" will be replaced  with
   the appropriate codes for a particular typesetter. (In this case, of
   course,  a warning isn't provided. EZ must assume your  macro--which
   may be used to substitute typesetting codes and/or ordinary text--is
   intentional.)

                             > and < Symbols
   These  characters normally aren't present on typesetting  fonts,  so
   should  be  avoided in ordinary text. Depending upon  your  specific
   typesetter, they usually should be reserved for "comment" and "flag"
   delimiters (which are the defaults, changeable from the installation
   main-menu  "*" function). Those going Beyond the Basics (Section  3)
   might  also use them to directly embed typesetting codes into  text.
   Because they should always be "paired," if EZ encounters a different
   number of one than the other, a warning message is issued.

                             Quotation Marks
   Computers  use one symbol--the " mark--to represent  both  beginning
   and ending quotes. Typesetting machines insert authentic,  different
   symbols  for  each.  So  EZ  makes  the  appropriate   substitution.
   (Defaults  are "" at the beginning of quotes and '' at the  end,  as
   used by some common systems. See main-menu "*" installation function
   to change.)
          Unlike  bold  and other commonly paired symbols,  EZ  doesn't
   report  unmatched  quote symbols. This is because rules  of  editing
   require  that quotations extending beyond a paragraph have  a  quote
   mark at the start of each paragraph, but only at the end of the LAST
   paragraph.
          Note  that  EZ must leave characters for single  quote  marks
   (used  for  "quotes  within  quotes")  as  they  stand  even  though
   typesetting  uses  different  characters to begin  and  end  "quotes
   within  quotes,"  because the end-quote mark for  single  quotes  is
   identical  to an apostrophe. EZ has no way to determine intent  with
   certainty. Macro keys may be used to insert appropriate codes, or  a
   "comment  to  typesetter" should forewarn each use of  single  quote
   marks for quotations.

                             Hyphens & Dashes
   The  distinction  between mandatory and "discretionary"  hyphens  is
   most  important,  and is carefully discussed in Section 2.  EZ  must
   assume   the  author  uses  discretionary  and   mandatory   hyphens
   correctly,  and  simply translates them  faithfully  to  typesetting
   equivalents.  (See main menu "*" installation function to alter  "="
   as  the default typesetting equivalent for  discretionary  hyphens.)
   For  dashes,  both  computers  and  typesetters  generally  use  the
   convention  of  two hyphens, so EZ passes  them  through  unchanged.
   Typesetters  generally  replace them with a  true  typesetting  dash
   during final output.

                               Spaces & <S>
   Note  discussion of "white space" in Section 2. . . .Because of  the
   radically  different way computers and typesetting  machines  handle
   spaces  (one  of  the reasons typesetting  is  so  beautiful!),  and
   because  word  processors  can use a single  storage  technique  for
   numerous types of white space, EZ helps by making a few  assumptions
   for   you--and  leaving  some  for  the  typesetter's   professional
   judgment.
          As  for the assumptions, a single space of course is  treated
   normally.  And  if the computer typist  followed  the  old-fashioned
   "rule"  of  two spaces between sentences, EZ  doesn't  complain.  It
   politely discards the offending second space.
          More  than  two spaces, however, probably  means  the  typist
   intended  something special. Maybe s/he pressed the TAB key  in  WS,
   which is represented with a fixed number of ordinary spaces (five is
   its  default, but that can be changed by the WS operator). Or  maybe
   the  line  was  centered. Or maybe it was a real  no-no:  maybe  the
   typist  was attempting to align a table. If the author  neglects  to
   contact  the  typesetter  in advance, the  latter  must  attempt  to
   determine intent by context or a call to the client. In any case, EZ
   helps  by  specifying the number of spaces, placing an  "S"  between
   delimiters  for each space character present in the  original  file.
   Example: <SSSSS>.
          Tips to typesetters: If "SSSSS" appears between delimiters at
   the beginning of a paragraph, the author probably meant indentation.
   (Em  spaces really should have been inserted with EZ's "FOLLOW  HARD
   RETURN"  option instead!) If a series of the symbols appears at  the
   beginning  of only occasional lines, the author probably  wanted  to
   center  text  instead  of properly using an EZ macro  or  leaving  a
   "comment to typesetter." (Maybe it's a headline?) If you see several
   consecutive  lines with a similar configuration of the symbols,  the
   author probably wants columns of data. You will need to touch things
   up.  (If the client is likely to submit similar jobs in the  future,
   you might want to pass along a few typesetting codes or tips to save
   time and effort next time.

                                   <NB>
   (WS  only)  This  is a special "nonbreak  space"  which,  if  placed
   between  two words, means the author doesn't want them separated  at
   an  end  of  line or column. The typesetter must  manually  fix  any
   paragraph containing this seldom-used WS function when reformatting.

                           Line Endings & <QL>
   WS,  WP,  ASCII  and typesetters follow  different  conventions  for
   storing "hard" and "soft" line endings in files. EZ ensures that the
   correct conversion is made (possibly after a one-time installation--
   see Section 4). Typesetters thus can reformat EZ files exactly  like
   their  own. (But for ASCII files, be sure to read  the  line-endings
   discussion in Section 2.)
          Left to its default, EZ precedes each "hard" line end with  a
   <QL> quad-left code, which may be changed or entirely suppressed  as
   discussed in Section 4. Hard line ends also may be FOLLOWED by codes
   --perhaps  to  add automatic paragraph indentation or  extra  inter-
   paragraph  leading  (space  between lines). Again,  see  Section  4.
   (Remember  how time consuming fixing "foreign" line ends was  before
   EZ? Not any longer!)

            "Comments to Typesetter" & WordStar "Dot Commands"
   Comments may be embedded anywhere in a file by placing them  between
   "comment" or "flag" delimiters ("comment" defaults of "<*" and  "*>"
   and "flag" defaults of "<" and ">" are user configurable).  Example:
   <*LIKE  THIS*>. The difference between the two is that  (subject  to
   possible  need  for initial EZ  installation)  "comment"  delimiters
   cause  the  typesetter  to ignore them  unless  explicitly  located.
   "Flag"  delimiters  (subject  to  the  same  condition)  forces  the
   typesetter  to  pause  for graphic arts  pro  consideration.  Unless
   requested  otherwise  by your typographer, we suggest  using  "flag"
   delimiters  to  set off  "comments to typesetter." EZ  passes  these
   through untouched.
          EZ also places all WS "dot commands" (lines beginning with  a
   period  in left-most column) within delimiters, since  dot  commands
   are not actual text. ("Flag" delimiters are default, but this may be
   toggled  with  main-menu function 7.) Dot commands serve  either  as
   formatting  instructions  for computer printers  and/or  screen--or,
   after  a ".." or ".IG" dot command, as WS' own "comment"  mechanism.
   Authors  should remember that typesetters may not be  familiar  with
   the  meaning  of dot commands. Normally, explain  their  meaning  in
   plain  English instead. However, if an author has a file to be  used
   both for computer printer and typesetter output (EASYTYPE makes this
   possible  for  the  first time!), the "dot command"  may  safely  be
   retained.  An ".." or ".IG" comment should be added explaining  your
   intent to the typesetter.

                <1> through <256> or <*1*> through <*256*>
   (WP  or WS only) The format--that is, whether appearing with  "flag"
   or  "comment" delimiters--depends upon the code-reporting  selection
   from the main menu, like above. The presence of these "number codes"
   calls for distinctly different reactions for WS versus WP files.
          With  a WS input file, you generally won't see any  of  these
   codes.  Likely,  the  file  simply  wasn't  created  in  WS'  normal
   "document" mode. (It should be. If WS' "nondocument" mode was  used,
   rerun  EZ  with ASCII mode instead as a lesser  alternative.  If  WS
   version  5.0  or  later was used, first use its  features  or  other
   method  to strip "graphic" codes.) Or, perhaps the EZ operator  used
   WP  mode on a valid WS file. (Shame! For most files, EZ  will  catch
   this--but  it's worth checking.) If in fact the file was created  in
   WS' "document" mode, it could refer to a couple of "user-defined" or
   specialty printer WS codes. But because these may have unpredictable
   meaning,  they should be avoided. Lastly, WS does accept  codes  for
   which  it  has no use of its own. But, even  though  total  computer
   addicts  could CONCEIVABLY find a value for this, it  should  NEVER,
   EVER be used for typesetting purposes. Typesetters who discover such
   symbols  in  files  which originated from WS  should  contact  their
   client.  Provide the precise location of the code and ask  what  may
   have been intended.
          (If  you discover an "undocumented" feature of  a  particular
   word processor that results in this symbol, please provide us with a
   copy  of  both the original word processor file and EZ file.  If  we
   modify  EZ to accommodate your tip, we'll send you  a  complimentary
   enhanced version.)
          In WS mode, these codes are really "insurance" provided by EZ
   for  your protection. Lesser programs passively place the  offending
   code  into  the output file (in some cases stopping  the  typesetter
   cold!)  or  discard it without warning (and perhaps  lose  important
   information).  . . .EZ warns of "unexpected" characters in its  end-
   run analysis screen.
          For  WP,  characters which result in "number  codes"  signify
   formatting  needs  of the WP program itself without  an  immediately
   translatable  typesetting counterpart. Or, in some cases,  they  may
   have such a counterpart but quality typesetting calls for discretion
   by a graphic arts pro. Working with a computer-printed copy on  hand
   is often helpful to typesetters working with WP files.
          Unlike  WS  "dot  commands," WP users  often  are  unable  to
   explain  the  meaning  of  "number  codes"  (or  even  know  they're
   present!), so a list of them is provided below.
          Though  exhaustive  explanation of "number codes" for  WP  is
   beyond the scope of this manual (and because usage changes as WP  is
   from  time to time revised), we can only briefly  describe  meanings
   here.  If  you encounter unlisted codes, please  see  "undocumented"
   features under the WS discussion immediately above. It is critically
   important  to report new WP codes, as they can be followed by  large
   amounts  of  "garbage" (from a typesetting perspective)  or  produce
   adverse output files (especially for WP beginning with version 5.0).
   With  your help and a copy of the original WP file, we  can  quickly
   update EZ to bypass related, unnecessary characters.
          Note  that  some "number codes"  have  "duplicate"  meanings,
   which relate to similar functions in various WP versions. Because WP
   beginning with version 5.0 contains elements which, until output  to
   normal  text files, aren't compatible with  typesetting,  "graphics"
   code  meanings for some of the following or additional number  codes
   aren't included here.

   WP "NUMBER CODES" DEFINED:
          [0 through 31 are computer "control codes." EZ translates  or
   reports  them,  depending whether typesetter intervention  might  be
   advised.]
          [32  through  126  are  ordinary  printable  characters  (and
   spaces), which appear in the file as such.]
          [127 and 128 should always have been removed from the file by
   WP. Their unlikely presence could be a pure computer malfunction, or
   the file wasn't created by WP, or EZ wasn't in WP mode. If rerunning
   EZ  doesn't correct the problem, please report all circumstances  to
   Advocate Enterprises.]
   <129>  Right justification on
   <130>  Right justification off
   <131>  End of centered text
   <132>  End of aligned or flushed text
   <133>  Temporary starting point for math calculations
   <134>  Center page from top to bottom
   <135>  Begin column mode
   <136>  End column mode
   <137>  Tab after right margin
   <138>  Widow/orphan control on
   <139>  Widow/orphan control off
   <140>  Hard end-line, soft end-page
          [141 processed by EZ, code suppressed]
          [142  and  143 are reserved by  WordPerfect  Corporation.  If
   discovered,  please  report these and provide copy of  WP  file  for
   analysis.]
   <144>  Red line on
   <145>  Red line off
   <146>  Strike out on
   <147>  Strike out off
          [148  and  149 refer to underscore  (italic).  EZ  translates
   them, then suppresses codes.]
          [150  and  151  relate  to  computer  screen  modes  and  are
   suppressed by EZ.]
   <152>  Table of contents placeholder
   <153>  Overstrike
   <154>  Cancel hyphenation of following word (strange!)
   <155>  End of generated text
          [156 and 157 refer to bold text. See 148/149, above.]
   <158>  Hyphenation off
   <159>  Hyphenation on
   <160>  Hard space character
   <161>  Do subtotal (Author should have entered subtotal manually!)
   <162>  Subtotal entry
   <163>  Do total (See 161)
   <164>  Total entry
   <165>  Do grand total (Again, see 161)
   <166>  Math calculation column
   <167>  Begin math mode
   <168>  End math mode
          [169 through 174 involve "soft" and "hard" hyphens in various
   circumstances. EZ translates each, then suppresses the codes.]
          [175  and  176  involve end of  text  columns  under  certain
   circumstances. EZ translates each, then suppresses codes.]
          [177 through 187 unused]
   <188>  Superscript
   <189>  Subscript
   <190>  Advance computer printer 1/2 line up
   <191>  Advance computer printer 1/2 line down
   <192>  Margin reset
   <193>  Spacing reset
   <194>  Left margin release
   <195>  Center following text
   <196>  Align or flush right
   <197>  Reset hyphenation zone
   <198>  Set page number position
   <199>  Set page number
   <200>  Set page number column positions
   <201>  Set tabs
   <202>  Conditional page end
   <203>  Set computer printer pitch/font
   <204>  Set temporary margin (indent)
   <205>  End of temporary margins (older WP versions)
   <206>  Set top margin
   <207>  Suppress page characteristics
   <208>  Set form length
   <209>  Page header/footer
          [210  used  by  older  WP  versions  for  footnote   contents
   themselves. Number code suppressed by EZ after processing.]
   <211>  Reset footnote number (older WP versions)
   <212>  Advance to half line number
   <213>  Set lines per inch
   <214>  Set extended tabs
   <215>  Define math columns
   <216>  Set alignment character
   <217>  Set left margin release
   <218>  Set underline mode (method of underlining)
   <219>  Sheet feeder bin number
   <220>  End of page function (complex data)
   <221>  Define columns
   <222>  End temporary margin
   <223>  "Invisible characters"
   <224>  Left/right temporary margin
   <225>  Extended character
          [226 used by newer WP versions for footnote/endnote contents.
   Number code suppressed by EZ.]
   <227>  Footnote options information
   <228>  Reset footnote number (later WP versions)
   <229>  Paragraph number definition
   <230>  Paragraph number
   <231>  Begin marked text
   <232>  End marked text
   <233>  Define marked text
   <234>  Define index mark
   <235>  Date/time function
   <236>  Block protect
          [237 through 240 not assigned or discovered in WP files]
          [241  and  243  are  two code found in  WP  v.  4.2,  meaning
   unknown.  We  found  no useful typesetting  purpose  after  detailed
   review. If found in files, please advise.]
          [242, 244 through 256 not assigned or discovered.]

                               "High Bits"
                   (For The Technically Inclined Only)
   Like many word processors, WS utilizes the "unused" eighth bit of an
   ASCII  character  for various purposes.  After  completing  line-end
   inspection  (since "hard" and "soft" line ends are identical  except
   for  the  eighth bit), and after looking for a  special  code  which
   tells WS to change the default left margin--a function  incompatible
   with  typesetting--EZ  resets the extra bit to  avoid  problems  for
   typesetters.
          WP  uses  most of the 128 possible computer  characters  with
   high  bits "on" for a different purpose--formatting codes. A  single
   character, a specific number of characters, or an unspecified number
   of characters until a specified terminating character is encountered
   tells WP something (e.g., "turn on bold" or "following is a footnote
   until terminator reached"). So for WP, EZ must identify what each of
   these codes is and handle it according to rules assigned to it.
          ASCII files in theory don't contain characters with high bits
   "on."  So  in  this  instance  EZ  discards  them  as   meaningless.
   Otherwise,  in ASCII files created with some operating  systems  you
   would  find  a  bundle  of such garbage characters  at  the  end  of
   virtually every file--a real nuisance for the typesetter!
          (Those  "funny  characters" you may have seen in  files  from
   time to time were caused by an unwanted eighth bit. For typesetters,
   those days are gone with EZ!)

   EASYTYPE END-RUN ANALYSIS & WARNING MESSAGES

   After translating a file, EZ provides a summary report, which varies
   according to the word processing mode in use (WordPerfect, etc.) and
   the nature of what EZ has determined.
          If it appears virtually certain the file being translated was
   NOT  created by the word processor whose mode was selected from  the
   main  menu,  EZ  skips its usual  statistical  analysis  and  simply
   advises of the problem. (The typesetting file IS, however, saved for
   review, if desired. In certain, rare cases the file might be usable.
   A  good "test" is to compare the size of input and output files.  In
   almost  all cases, a valid output file will be the same size  as  or
   larger  than  the  input  file.  If  substantially  smaller,  almost
   certainly the output file is useless.)
          IMPORTANT  NOTE: The mentioned general file-format  tests  do
   NOT  apply  to  Generic/ASCII mode. So be  careful  that  you  don't
   inadvertently  use this mode for other files. Noting file  sizes  is
   always a good idea!

          For  input files which appear proper, EZ provides a  detailed
   analysis--and possibly warning messages.
          The first statistics summarize work performed--the amount  of
   which may shock you, especially for WS and WP files!)
          EZ then reports whether any "bad" characters were encountered
   and marked. The discussion above about <{>, <#>, etc. describes most
   of these. These aren't errors, but are cause for rewriting text  (in
   some  cases), or selecting typefaces which accommodate  them  (other
   cases).  This warning also refers to potential errors  and  problems
   (see discussion under "<1> to <256>," above).
          For  WP,  starting and ending  footnote/endnote  numbers  are
   shown.  If you have related files which continue the same  numbering
   scheme,  note  the highest number reported so you can  continue  the
   numbering correctly with Options Menu 1 for the next file.
          Then,  for WS or WP, a section reports whether the number  of
   bold,  italic  (underscore)  and  (for  WS)  "double-strike"   codes
   matched.  If  not, it's almost certainly unintended  and  should  be
   corrected before typesetting. The "start-bold" and "end-bold" codes,
   for  example, placed in the output file by EZ almost certainly  will
   be incorrect after the point of author error. You may want to locate
   the  error by searching for <BOLD> codes and inspecting  for  nearby
   <MAIN> codes. If you don't find the latter for an extended  section,
   you've  probably  located the error, and may be  able  to  determine
   where a title or whatever should have a <MAIN> ending symbol. If so,
   it's wisest to correct the problem with the original word processing
   program, then use EZ again.
          Similarly,  for  all word processor modes,  EZ  then  reports
   whether the angled brackets characters ("<" and ">") generally  used
   for  "comments  to typesetter" and specific typesetting  codes  also
   were  paired. If not, disaster may lurk unless the error  is  found!
   (If  they  aren't paired, the number of left and right  symbols  are
   reported so you will know how many potential problems to fix.)  Note
   that any angled brackets inserted through  EZ Options Menu functions
   are NOT checked for pairing, permitting maximum power by experienced
   users.
          Then,  EZ reminds you of the word processing mode  and  code-
   reporting  format  in  use. If an unusual  number  of  warnings  are
   indicated  by EZ statistics, it's particularly wise to  double-check
   the word processing mode to ensure the wrong one wasn't selected.
          For  files larger than about 20K (which create  problems  for
   some  typesetters--even loss of data without notice in  microVISION)
   EZ  displays  a  flashing  filesize as a  warning.  In  such  cases,
   consider  using  the original word processing program to  break  the
   file into smaller ones--then rerun EZ.
          Lastly, EZ asks whether you want to return to the main  menu.
   If you respond negatively, EZ returns you to the operating system.
~ (Section 7)
                       << USER-ADDED INFORMATION >>

          Graphic  arts studios and computer dealers with  an  EASYTYPE
   resale  distributorship  license, as well as licensed  EASYTYPE  end
   users, may add notes and other information for their purposes  here.
   Begin  by  following a basic computer precaution of editing  ONLY  a
   back-up  copy  of EASYTYPE.HLP. A word processor  capable  of  ASCII
   output must be used. (For WordStar, select "nondocument" rather than
   normal  "document" mode from its main menu when creating your  file.
   For  WordPerfect,  save the output file in "DOS" format.)  NOTE:  Be
   sure all text remains BELOW the line "<< USER-ADDED INFORMATION  >>"
   and  ABOVE the (undisplayed) line "~(Section 8)." Failure to  follow
   these precautions may cause adverse effects when EASYTYPE.HLP is run
   by EZHELP.EXE or EZHELP.COM.
~(Section 8)
              << LICENSE AGREEMENT, CREDITS & DISCLAIMER >>

   EASYTYPE.EXE, EZHELP.EXE, EZ-SHARE.EXE, AEORDER.EXE,  (EASYTYPE.COM,
   EZHELP.COM EZ-SHARE.COM and AEORDER.COM for some operating systems),
   EASYTYPE.HLP,   README.COM,  EZMONEY.COM,  plus   all   accompanying
   materials  (together referred to as "EASYTYPE" below) are  copyright
   (c)  1986-90,  J.W. Olsen / Advocate Enterprises, Ltd.,  all  rights
   reserved.  By  use  of  EASYTYPE,  user  agrees  to  all  terms  and
   conditions herein, which constitutes our full agreement.
          J.W. Olsen / Advocate Enterprises, Ltd. has taken due care in
   preparing EASYTYPE. However, no expressed or implied warranty as  to
   accuracy, reliability or suitability for any specific purpose or use
   is  made. In no event shall J.W. Olsen / Advocate Enterprises,  Ltd.
   be  liable  for  damages,  including  incidental  or   consequential
   damages, in connection with or arising from furnishing, performance,
   support or use of EASYTYPE.
          Upon  payment  of the registration licensing fee  ($49.95  at
   this writing), J.W. Olsen / Advocate Enterprises, Ltd., will provide
   the  latest, full-featured version of EASYTYPE and  associated  help
   files,  a  program  to convert Configuration Files  from  all  prior
   EASYTYPE  versions  to  that  of the  latest  version,  90  days  of
   reasonable  telephone  and modem access support, an  opportunity  to
   earn a tidy sum for introducing others to EASYTYPE and EASYDATA,  as
   well  as  notification  of future updates and  access  to  same  for
   copying/mailing charges only ($10 as of this writing).
          You agree not to distribute any full-featured (as opposed  to
   shareware)  version  of  EASYTYPE  without  the  expressed,  written
   permission  of  the  copyright holder.  Unregistered  users  of  any
   version may not use them for financial gain. Others may use them  AT
   ONE  SITE or BY ONE INDIVIDUAL, but NOT BOTH. Subject to  the  other
   terms and conditions herein, users are authorized to make sufficient
   copies  of EASYTYPE for normal use by the one individual or  at  the
   one site.
          Users  who  have received a complimentary copy of  the  full-
   featured  EASYTYPE may not sell or otherwise transfer it to  another
   party.  Other users may transfer EASYTYPE (original disks  only,  in
   the case of full-featured versions) to another party, provided  such
   users  and the subsequent owners agree to all terms  and  conditions
   herein, and provided all EASYTYPE materials are transferred together
   and without alteration. Further, by resale of any copy of  EASYTYPE,
   seller agrees to relinquish any right to further possession, use  or
   ownership of said copy or any duplicates made of same.
          For further information and ordering (including bulk rates or
   distributorships), see AEORDER and EZMONEY, or contact:

                 J.W. OLSEN / ADVOCATE ENTERPRISES, LTD.
                     899 S. Plymouth Court, Suite 504
                            Chicago, IL 60605
                          312/939-3300  (voice)
              312/939-4411 (24-hr. modem telecommunications)

   Credits:
          EASYTYPE, EASYDATA, EZHELP, EZ-SHARE, AEORDER and EZMONEY are
   trademarks  of J.W. Olsen / Advocate Enterprises, Ltd. EZHELP  is  a
   dedicated version of HELP.EXE (HELP.COM for some operating systems),
   copyright (c) 1986-89, J.W. Olsen / Advocate Enterprises, Ltd.,  all
   rights reserved. A full-featured version is available for sale  ($20
   at this writing), accompanied by instructions to easily create  help
   files  on  unlimited topics for use in your office or home  with  an
   ordinary word processor.
          MicroVISION is a trademark of CyberTEXT Corporation. WordStar
   and WordStar 2000 are registered trademarks of MicroPro Corporation.
   WordPerfect is a registered trademark of WordPerfect Corporation.
~